Conversation
Co-authored-by: Abdo <abdo@abdnh.net>
1. build/configure/src/main.rs: Removed extra blank line (Rust fmt) 2. README.md: Fixed dprint formatting (blank lines, spacing) 3. build/configure/src/web.rs: Added .venv to fmt_excluded glob so the build system ignores venv files 4. .gitignore: Added .venv
| "option-ext", | ||
| "redox_users 0.5.2", | ||
| "windows-sys 0.60.2", | ||
| "windows-sys 0.59.0", |
There was a problem hiding this comment.
cargo update -p rustls-webpki and cargo update -p tar were apparently needed due to failing GHA checks.
Documentation build overview
Show files changed (2 files in total): 📝 2 modified | ➕ 0 added | ➖ 0 deleted
|
|
Follow-up: Include generated code in docs The current RTD setup only documents source-level Python (pylib/anki, qt/aqt). The old Sphinx config also included out/pylib/anki and out/qt/_aqt, which contain ~30k lines of generated code that's arguably the most valuable to document for add-on developers:
Generating this code requires ./ninja pylib qt, which needs Rust toolchain, protoc, Node.js, etc. — not feasible in RTD's build environment. Proposed approach for follow up task: Use a GH Actions workflow to build the docs instead of (or in addition to) RTD:
This would give the docs site the generated hooks and protobuf types, which are what add-on developers most need documented. |
3 participants
Closes #4578
Docs can be viewed here: https://dev-docs.ankiweb.net/en/latest/
Or built and viewed locally with
just docs-serve